@mdhont done

Hello,

I have been working with this container recently and have applied a work around which also creates and configures the keyfile before mongod is started. This PR would definitely help.

I noticed that you have moved mongodb_set_listen_all_conf to before the initial startup. I was thinking this has a (miniscule) risk of letting mongod accept external commands before the initial users had been created.
The option here is to leave it where it is so that the first time mongod is run it is bound only to local host.

(In my scenario i am passing --transitionToAuth in as an extra flag which requires authorisation to be enabled. To stop mongod failing on the first run through I enable auth through mongodb_set_keyfile_conf. Since enableLocalhostAuthBypass is still enabled for the initilization the root user is still created despite auth being required at that point)

Good point @dtrts. I've made the suggested change, and left the listen-all configuration where it was.

Bump

@mdhont is the review underway or scheduled?

The solution is failing in our internal tests, and it needs some further investigation to find the cause.

@mdhont thank you for the update.

This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.

This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.

@rrileyca, the license-header-linter job is failing, which is checking if some files contain a needed header. As this has recently been added could you sync your fork and do a rebase on the main branch?

@mdhont Done! Thanks for reviewing.